-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(node/rucio01.ls.lsst.org) deploy rucio #1488
base: production
Are you sure you want to change the base?
Conversation
0f0bedc
to
ecb9a51
Compare
57112a3
to
84f370e
Compare
]: | ||
ensure => file, | ||
mode => '0644', | ||
owner => 'saluser', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is saluser
being used as the role user? This isn't a tssw related service and it doesn't interact with sal/dds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They want to use saluser
as a service account to manage the xrootd related services.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the ownership of these files to saluser
does not allow the saluser
to start or stop those services. Nor does it grant saluser
the ability to trigger systemd to re-read those files after they have changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also object to role accounts editing service units. Changes should be made via puppet.
b2eda09
to
02fb506
Compare
02fb506
to
178c315
Compare
Requirements per ticket information on IT-5509:
• Install the following rpms, xrootd, xrootd-selinux, xrootd-libs, xrootd-client, xrootd-client-libs, xrootd-server-libs, xrootd-server
• modify the /lib/systemd/system/[email protected] and /lib/systemd/system/[email protected] and change the User and Group inside these two unit files to saluser and it group (current it is user xrootd)
• Change the owner of directory /etc/xrootd, /var/{log, run, spool}/xrootd to saluser (this probably need to be done every time there is an update of the xrootd rpms)
• Allow user bwhite and wyang to do a) sudo su - saluser and b) sudo systemctl restart xrootd@summit. We will add Sajid Ali to this list of users once he has an account
• Place VM in BTS-LHN network.
• Mount the filesystems KT mentioned.